home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
email
/
albert.exe
/
EEMAIL.DOC
< prev
next >
Wrap
Text File
|
1993-08-30
|
32KB
|
728 lines
██▐███ ██▐███ ██ ██ █▐███ ██▐████ █▌████
██ ██ ██ ██ ██ ██ ██ ██ ██ ██
██ ██ ██▐█ ██ ██ ██ ██ ██ ██ ██
██ ██ ██ █▐ ██ ██ ██ ██ ██ ██
██▐███ ██▐███ ▐██ █▐███ ██ ██ ██
██▐███ █▐███ ██▐███ █▌████ ██ ██ █████ ██▐███ ██▐███
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██
██▐███ ██ ██ ██▐█ ██ ██ █ ██ ██▐████ ██▐███ ██▐█
██ ██ ██ ██ ██ ██ █ ██ ██ ██ ██ ██ ██
██▐███ █▐███ ██ ██ █▐███ ██ ██ ██ ██ ██▐███
74 Trevino Lane
Conroe, Texas 77302
Business (409) 273-3220
BBS (409) 273-3112
NHUB: JIM@DEVONT
╒══════════════════════════════════════╕
│ Welcome to Einstein Electronic Mail! │
╘══════════════════════════════════════╛
Thank you for looking at Einstein E-Mail! We appreciate the
time and effort you spend in looking at our software. You'll discover
we really make an effort to ensure your time is well rewarded.
Since its inception in 1990, Einstein has seen quite a few revisions
and user-inspired changes and upgrades. With the help of our users and
beta-testers around the world, we've grown from a proprietary
messaging solutuion to an industry-standard MHS-compatible electronic
messaging and workgroup product with clients ranging from Fortune 100
conglomerates to "mom-and-pop" neighborhood operations. Einstein
can be found changing messages on the world's most advanced network
systems and handling the messaging requirements of thousands of network
clients around the world.
Einstein comes in two flavors: DOS and Windows. Both versions
can exist on the same network and be in use at the same time.
As of this writing, only the DOS version is available in 30 day
evaluation versions. For information on the Windows product,
please call our Sales department, or see PC World July 1993
for a review. As well, we are reviewed in Windows Magazine,
Computer Shopper and others in July and August 1993.
This version of the program does not include complete documentation
for the users or the systems administrator. Experienced Novell
Systems Administrators should have no problems setting up the system
for Einstein use.
If you should require more assistance than this brief documentation
provides, please call Devont Software's BBS at (409) 273-3112
(300-9600 bps, 24 hours a day). You can download a complete electronic
reference from our file areas. We are happy to provide you with
assistance in setting up the program for your use. If you are an
NHUB user you can reach us by sending mail to SUPERVISOR@DEVONT.
CompuServe users can reach us with email at [70421,1506].
┌──────────────┐
│ Requirements │
└──────────────┘
Einstein requires an IBM PC/XT, AT, PS/2 or compatible computer with 512K
RAM or more. Although Einstein will run on an XT-class system, a 286 or better
is recommended. Monochrome, Hercules, CGA, EGA, VGA and Super VGA video
modes have been tested and supported. Networking software is also required.
Novell Netware 286 and 386 has been tested and supported. ELS versions
have been tested and are supported. You'll need 470K RAM or more to use
all of Einstein's feature.
If running Einstein in TSR mode, you should be using a 286 or better workstation
with 2M RAM and an XMS or EMS memory manager.
Each workstation's CONFIG.SYS file should contain at least the following
information:
FILES=20
BUFFERS=20
After loading the network shells, you should have at least 470K RAM free in
order to run the program. Networks with a lot of objects in the bindery
(users, groups, printers, etc) may require a bit more free RAM.
On the average, a 100 user network requires 470K RAM Free or more to run
all modules of the program. If you are using a menu system that takes
up low memory, be aware of the memory requirements of your menu system!
Examples of menu systems that use up low DOS memory are Novell's menu
and WP Office menu. Saber menu users should use the "BATCH" option from
the program option line.
If you are going to communicate with other email systems, you'll need
Novell's Message Handling Service (MHS) program and an MHS server on
your network. MHS is available from your Authorized Novell Dealer.
Call 1-800-RED-WORD for details on acquiring MHS.
┌──────────────┐
│ Registration │
└──────────────┘
Einstein is not free software! You are granted a limited license to preview
the software for 30 days. After 30 days, Einstein will stop working on
your network. To purchase a live copy, please see the order form
included in this document or call us at (409) 273-3220 to place an order.
With your order, you receive a complete boxed set: Manuals, distribution
diskettes, warranty and licensing information, BBS access, tech support
and a commitment to making your system a success!
If you have any comments or questions, please call Devont Software's BBS
at: (409) 273-3112. We support 300-9600bps 24 hours a day, 7 days a week.
Or call our technical support staff at (409) 273-3220 between 9 and 5 CST.
Thank you for your time and effort in looking at this software. IF IT IS
NOT FOR YOU, PLEASE PASS ALONG THIS PROGRAM AND DOCUMENTATION TO SOMEONE
ELSE WHO MAY BE INTERESTED.
Devont Software Inc.
74 Trevino Lane
Conroe TX 77302
Order Form
Sold To: ____________________________________________________________________
Company: ____________________________________________________________________
Address: ____________________________________________________________________
City: ____________________________ State: __________ Zip Code: __________
Phone: ___________________________________ Data: __________________________
Netware Version: _______________________ Number of Users: __________________
Current Einstein Version: ________________ Obtained From: __________________
[ ] Copies Einstein E-Mail Unlimited (Per Server) @ $699.00 Each __________
[ ] Copies Einstein E-Mail 50 Users (Per Server) @ $499.00 Each __________
[ ] Copies Einstein E-Mail 20 Users (Per Server) @ $399.00 Each __________
[ ] Copies Einstein E-Mail 10 Users (Per Server) @ $299.00 Each __________
Residents of Texas add Sales Tax (7.25%) _________
Shipping and Handling $10.00
Outside of US (except Canada) $20.00
Total Price _________
Please send remittance in form of Check or Money Order to:
US/Canadian Banks and US Currency Only, Please!
Devont Software, Inc.
74 Trevino Lane
Conroe, Texas 77302
(409) 273-3220
>> Please allow two weeks for delivery <<
We welcome your comments! In the space provided below, please tell us what
you like about Einstein, what you don't like, what you'd like to see added,
and/or what features convinced you that Einstein was the product for you:
-----------------------------------------------------------------------------
┌──────────────────────────────────┐
│ Novell Installation Instructions │
└──────────────────────────────────┘
To install Einstein on your network, follow the steps below:
1. Create a directory for the mailboxes. Einstein is flexible, in that you
may choose any volume in which to store the data. For example, if you
want to install the data files on SYS1:, type the following:
map m:=server/sys1:
m:
md\Einstein
cd\Einstein
copy a:*.*
Note: You can install Einstein in the existing SYS:MAIL directory if
you desire. If you do, you still have to grant trustee rights
(Minimum rights = RWOSCM) to this directory for all Einstein users
in order to run the program.
We recommend that you install Einstein somewhere else on your network,
though. SYS:MAIL\user contains other files pertaining to login
scripts and printer defaults. It would be wise to separate Einstein
from these other data files if you ever want to uninstall Einstein.
2. FLAG the files appropriately. Mark all files as SRW. For example:
FLAG *.* SRW You can flag executable files SRO if you so desire,
but all other files should not be write protected as Einstein opens
and writes to these files frequently. If you are concerned that
users may inadvertantly delete files, you can use Netware's DI
attribute to prevent these files from being removed.
3. ATTACH to all servers on your network as SUPERVISOR or equivalent if
you are planning to install a wide-area email network. You don't
need to attach to a server on which you do not plan on installing
Einstein.
4. Run the ADMIN.EXE program. You must be a SUPERVISOR or equivalent.
ADMIN senses a new installation and prompts you to continue with
a "yes/no" dialogue box. Choose "Yes" to continue.
5. A listing of all attached servers displays. Press <Enter> on each
server that you would like to be included in the UserList and valid
user tables. At the "Server Name" prompt:
If you are running MHS, name each server whatever you called it
in MHS' routing table. This is the server's Mail Name. It
can be different from it's physical name, have your MHS installation
information handy if you are going to be using these features.
If you are not running MHS, you can simply accept the server's
default physical name.
When you have completed building your server table, press
the <Esc> key to return to the ADMIN main menu.
6. Again from the ADMIN main menu, select "Maintain User/Group List"
then select "Edit User List." The user database displays. Users
that do not need to have a mailbox can be "Excluded" from the
list by pressing <Alt>+<X>. For example, you should exclude
GUEST, print server accounts, batch server accounts, or other user
or group accounts that you do not want to show up in the user
listing. Return to the Main menu by pressing <Esc> when you
have excluded all you need. Excluded users will not have a mailbox
on the system and take up no space.
7. Select "Create Mailboxes." This program will create necessary data files
for each user account on the network. Excluded users will be skipped.
Any existing Einstein data is not affected by this procedure, should
you ever re-run this function.
8. Create a .BAT file for the users to access the program. You can be as
creative as you like, but keep in mind that the user MUST be placed in
the directory created in the first step in order to access his mailbox.
For example, if you elected to store your mail data in SYS1:, create a
.BAT file similar to the following:
echo off
cls
echo Loading Einstein E-Mail...Please wait...
map m:=sys1:Einstein >>nul
m:
maild
...return to home dir and menu..
If running in TSR mode (please see "Running in TSR Mode" below) :
echo off
cls
echo Loading Einstein E-Mail...Please wait...
map m:=sys1:Einstein >>nul
m:
maild /t c:\
...return to home dir and menu..
The .BAT file you create should be placed in a common directory, such
as SYS:PUBLIC (usually defined as Z:) so all users can run it.
9. Assign Trustee assignments to the directory in which the mail data files
are to exist. The users must have ALL RIGHTS, except Supervisor and
Access Control (Or Parental, for NW 2.x). For example, if you placed
the Einstein data files in SYS1:Einstein, run SYSCON, create a group called
Einstein, and assign Trustee Directory Assignments for that directory. Add
ALL Einstein USERS to this new group.
If you need more information about running the SYSCON utility, refer
to the Netware Systems Adminstration manual or give us a call on our
technical support lines. We'd be happy to help you set up your system!
You could if you prefer, assign the group EVERYONE trustee directory
assignments to this directory without having to create a new group.
10 Create a Netware group called "EESUPER" (using the SYSCON utility, of
course). Make yourself and other supervisors, as well as those users
you wish to have some degree of email supervision a member of this
group. For instance, an EESUPER member can view the telephone log
file and erase Public Folder messages.
11 You're ready to run the program! Change to the Einstein directory you
created and installed into, then run the MAILD.EXE program to check
it out!
┌──────────────┐
│ Please Read! │
└──────────────┘
Need more information? Yes, we know this documentation is skimpy. We're
confident that you can operate the program without documentation, but if
you need more info, please call us! Operators are standing by....
Complete documentation and help files are available on our BBS. You can
download the EEDOCS.ZIP file and print it using WP5.1 and an HP LaserJet
III or compatible printer. Context-sensitive HELP files are also available
for your downloading pleasure.
┌─────────────────────────────┐
│ Using Einstein's MHS Features │
└─────────────────────────────┘
Einstein is an MHS-compliant mail system, meaning you can use the package
to commicate with email systems across the country, or connect to
message hubs such as Compuserve or Novell's NHUB message clearinghouse.
Einstein requires no special setup to accomplish this, only the following
environment variables be defined for each workstation:
MHSPATH The drive and colon for locating the MHS directories.
MHSNAME The name of your MHS hub.
A good place to set these variables is in the System Login Script (SYSCON).
For example, add the following lines to yours:
SET MHSPATH="h:"
SET MHSNAME="MHS_NAME" (Replace "MHS_NAME" above with your MHS Hub name)
Before running Einstein, you need a pre-existing drive mapping to whatever
drive you specified in the MHSPATH environment variable above. For example,
add the following to your System Login Script:
MAP h:=sys:
If the MHS server is connected to a server that is not your default server,
you'll need to attach to that server before creating the drive mapping. If
all users do not have an account on the server in which the MHS server
is located, you must create one for each user on the server, and use that
connection to facilitate the drive mapping. The MHS installation will
create proper trustee assignments for each of the users automatically.
Assign no password to the account so the Login Script can perform the
connection without prompting the user for a password. For example:
SET MHSPATH="h:"
SET MHSNAME="MHS_NAME"
ATTACH MHS_SERVER/%LOGIN_NAME
MAP h:=MHS_SERVER/sys:
Finally, you need to install MHS per the instructions found in the
MHS manual. If you require assistance, please call our technical support,
your dealer, or Novell for specific MHS installation instructions.
┌───────────────┐
│ Routing Setup │
└───────────────┘
ADMIN allows you to set up remote Routing Tables to ease in sending mail
to remote users or groups. For instance, if you have several users on
a remote system that you would like to be able to refer to as "Sales"
while creating a message, you can use ADMIN's "Maintain User/Group List"
feature to specify the complete route name of each of the members, and
this group will appear in the User List of all network users. Assume
the remote MHS connected server hub is called "DENVER." You could set
up a route to the remote group like:
User ID: SALES
Server: REMOTE (can be anything, is only used for UserList purposes)
Dist. List: BOB@DENVER,MARTY@DENVER,SAM@DENVER,SALLY@DENVER,ALEX@DENVER ...
Keep in mind that MHS is limited to having 64 addresses in the Send To:
field. If communicating with a large network through MHS, you should
consider breaking down the remote lists into managable groups so this
limit is not exceeded.
┌───────────────────┐
│ Demo'ing Einstein │
└───────────────────┘
If you just want to preview the program, and do not want to create a
mailbox for each and every user on your network, ADMIN will allow you
to create one mailbox at a time. Here's what you do:
Enter the Einstein data/program directory. Type "ADMIN /c USERID" (without
the quotes). Do this for a couple of users, including yourself, and
then run the MAIL program. Of course, you will only be able to send and
receive mail to/from those user accounts that you created from the command
line.
┌──────────────────────────┐
│ Upgrading Older Versions │
└──────────────────────────┘
If you are ugrading from versions prior to 2.0, you should basically erase
your old data and reinstall the new one.
Otherwise, to upgrade from older versions simply follow the installation
instructions. This procedure will not overwrite your existing user data
files.
┌───────────────────────────┐
│ Flagging Mail Directories │
└───────────────────────────┘
For Netware 386 users, the mailbox directories created during the installation
procedure should be flagged PURGE. This will decrease the amount to server
resources required to track all of the deleted files (which in any mail system,
is a lot of files!). To flag all the user mailbox directories, perform the
following (you must be a SUPERVISOR or equivelent!)
cd sys1:mail
FLAGDIR *.* PURGE (you could also add HIDDEN here if you desire)
If running MHS, you should also flag the MHS user directories as well as the
SND directory as purge. For instance:
cd sys:mhs\mail
flagdir snd P
cd sys:mhs\mail\users\USERID
flagdir *.* p
┌────────────────────────────────┐
│ Einstein E-Mail Administration │
└────────────────────────────────┘
Einstein is very easy to administer. After you have created all the mailboxes
for the user accounts, there is very little that needs to be done on a
regular basis. If you add users to your system, you will need to run
the "Create Mailboxes" function in the ADMIN.EXE program to create a
new mailbox for the user. If users already exist on your system, they will
not be affected by this procedure. Only new user accounts will be added
to the system. Note again, that you must be in the Einstein data directory
to perform any of the administration duties. Running the program anywhere
else will create new mailboxes in whatever directory you are currently
in.
┌───────────────────┐
│ Packing Mailboxes │
└───────────────────┘
When users delete messages from their system, Einstein removes the message
record, but leaves the message text in the data files. This is done
purely for performance reasons. System Administrators need to "pack" the
user mailboxes at regular intervals. We recommend that this procedure be
be run at least once a month. To pack the user mailboxes:
1. Change to the Mail Data directory. If you elected to store the data
files in SYS1:\Einstein, type:
map m:=sys1:Einstein
m:
ADMIN
2. Select "Pack Mailboxes." An informative message displays, then you
are prompted with a "yes/no" box. After you have read the message,
select "yes" to perform the procedure.
3. Next, you are prompted if you would like to remove old messages. Old
messages are those that have already been read (OutBox messages are
always considered "old" messages). If you would like to remove
messages that are older than 90 (or whatever you specify) days, select
"Yes". If not, select "No."
If you choose "Yes," you are prompted to enter a number. This number is
used to scan the InBox and OutBox, and all messages which are older than
this number of days are removed from the system. Note that WasteBasket
messages are automatically removed after 10 days, so this procedure
does not affect those messages.
If you choose "No," the packing procedure will continue, and all messages
will be retained.
The packing procedure should be run when no users are accessing their
mailboxes. If a user has a mailbox open at the time this procedure is
run, that mailbox will be skipped. Not a mojor event, but it is recommended
that this procedure is run during off peak hours mainly because of the
increased traffic that occurs during the packing procedure.
For this reason, ADMIN allows you to specify parameters at start up to
allow you to run the packing procedure at a specified time. For instance,
you could let ADMIN pack all the mailboxes at 2am, when it's likely that
no one will be using the mail system. To do so, enter the following while
in the Einstein data directory:
ADMIN /p 02:00
The program will then go into "AutoPack" mode, waiting until 2am to perform
the procedure. The TIME parameter is in 24 Hour military time.
You can also "pack" one user's mailbox at a time from the command line. This
is to assist the administrator in recovering corrupted index/data files. To
use this feature, type the following while in the Einstein data directory:
ADMIN /p UserID
Where UserID is a valid user of the network. If the user does not have
any data files, nothing will be performed. The ACTIVITY.LOG file is
updated to show packing activity messages. You can view this file or
print it out to view any error messages.
┌────────────────────────┐
│ Excluding Users/Groups │
└────────────────────────┘
Einstein allows the system administrator to exclude certain users or groups
from the mailing lists. You may have set up groups that you do not want
users to send mail to, such as print server accounts, remote groups, etc.
By default, Einstein Excludes the user account GUEST from all mailing lists,
and will not allow a user to send mail to that account. To exclude additional
users or groups from the mailing lists, perform the following:
1. Enter the drive/directory where the Einstein data files exist.
2. Run the ADMIN program by typing ADMIN at the command line.
3. From the ADMIN main menu, select "Exclude Users." A pick-list of
user accounts will display. Currently excluded users and groups
will have an asterisk (*) in the left-most portion of their name.
4. Using the cursor keys, move the highlight bar to a user/group account
that you would like excluded. Press the <Del> key. A pop-up menu
box displays, confirming your selection.
Repeat the above steps for each user you would like excluded from the mailing
lists.
If you would like to re-include a user that you have previously excluded,
perform the following steps:
1. Enter the drive/directory in which the Einstein data files are stored.
2. Run the ADMIN program by typing ADMIN at the command line.
3. Select Exclude Users/Groups.
4. Using the cursor keys, move the highlight bar to a user/group account
that you would like included in the mailing lists. Press the <Ins>
key. If the user is not already included, you will be prompted with
a pop-up menu box, confirming your selection. Selecting "Yes" will
re-include the user in the mailing lists.
5. Create a mailbox for this included user (if not already created). You
can accomplish this by using the "Create Mailboxes" function or by
using the "/c" parameter on ADMIN's command line. For example,
ADMIN /c JIMT creates a mailbox for the user JIMT.
If you would like to start over on the EXCLUDE lists, simply delete the
EXCLUDE.DBF file located in the Einstein directory. If this file is removed,
only the GUEST account is excluded from the mailing lists.
┌────────────────────────┐
│ Removing User Accounts │
└────────────────────────┘
If you delete a user from your network, you can use ADMIN's "Maintain
User/Group List" feature to remove the user from the list and delete
his mailbox from the system at the same time. Press the <Del> key
while in the User/Group list to see.
┌─────────────────┐
│ Using PrintMail │
└─────────────────┘
A unique feature to Einstein E-Mail is the "PrintMail" feature. If you
have users in your office that do not have access to a computer on the
network, but would still like to receive mail messages from other
users, you can specify a valid print queue in their user definition,
and all incoming mail and phone messages are routed to this printer instead
of a mailbox.
To set up a PrintMail account, select "Change User Information," move
the highlight bar to a user, and type the name of the print queue in
the "Delegate Mail To:" field. All incoming messages are automatically
routed to this print device.
┌──────────────────┐
│ Using CKMAIL.EXE │
└──────────────────┘
CKMAIL.EXE checks the currently logged-in user account's mailbox for unread
messages. CKMAIL returns the following DOS ERRORLEVEL:
0 = No New Mail waiting
1 = New Mail Waiting
2 = User has no InBox
3 = Phone Messages Waiting
CKMAIL.EXE should be run in conjunction with a .BAT file. CHECK.BAT is
included in the archive file as a sample. If you have LANTools (also
found on our BBS), you can make an interactive mail checking system that
uses the same interface properties as Einstein. Check it out!
┌──────────────────────────────┐
│ Running Einstein in TSR Mode │
└──────────────────────────────┘
Einstein can be made to run in Resident mode. By specifying parameters on
the Einstein command line, you can make Einstein a TSR (terminate and stay
resident) program.
Since Einstein uses a method to swap program code into extended or expanded
memory, Einstein should only be run in TSR mode on 286/386 machines with
at least 2M bytes of RAM. You must be using an extended or expanded memory
manager, such as HIMEM, EMM386, QEMM, 386MAX or QRAM. Performance will
suffer if run on any other class of machine, or no EMS/XMS memory is
available. Extended memory is preferred, so if you've got HIMEM.SYS
lying around, put it in your CONFIG.SYS and go! If you have enough
high RAM and are using it all as Expanded memory, it's a good idea
to save some of it for Extended memory. You'll need to keep at least
640K Extended or Expanded for optimal results.
See your memory manager documentation for details on this, or call us.
We've worked with HIMEM, QEMM, 386MAX, and EMM386 and others and can probably
help you along.
Parameters for Einstein TSR Mode
/T Start Einstein using TSR mode
path Path to write temporary swap files. If Einstein does not find
enough EMS or XMS memory to swap in program code, a disk file
will be created. Specifying this parameter tells Einstein where
to look for those files. If this parameter is omitted, the
current drive/directory is used. Note: Writing Swap files
to a network volume can create excessive network traffic!
Example: MAIL.EXE /T C:\
This tells Einstein to run in resident mode, and write any temporary
swap files to the C:\ directory.
If this setup does not meet your needs, Einstein operates works just fine
with other memory-switching programs, such as Software Carousel, MicroSoft
Windows, and most others...Just make sure you run Einstein without the
/T and path parameters when using such programs.
Notes
If you load Einstein resident from your memu system, Einstein may not allow you
to unload it while the menu is running (we're working on getting around
this slight problem). If this is the case, you may only be able to unload
Einstein while hot-keying from the DOS prompt. If your users cannot access
the DOS prompt, make sure their machine is rebooted when they leave the
menu system. No harm will be done to the Einstein data files if this happens.
A good tool to log one off the network then reboot the computer is Devont
Software's LANTools (no plug intended). You can get this utility on our
BBS, on CIS, or networking BBS' all over...
┌───────────────────┐
│ Using MAILPOP.EXE │
└───────────────────┘
If Einstein is already active, and the user invokes the program again,
a DOS ERRORLEVEL of 1 is returned, and the program ends. You can test
this ERRORLEVEL in a batch file, then simulate the pressing of the
ALT+INS key with MAILPOP.EXE. The following batch file illustrates
how to incorporate this into your environment:
*** Einstein.BAT ***
@echo off
cls
map m:=sys1:mail >>nul
m:
mail.exe
if errorlevel 1 MAILPOP.EXE
Using this method, you can place one entry on your network menu for Einstein.
If a user selects this menu item and the program is already loaded, the
DOS ERRORLEVEL of 1 is returned and you can simulate the ALT+INS keystroke.
You can also use this same procedure to automatically invoke Einstein upon
initial invocation of the program. In other words, if you want to make
Einstein resident and enter the program at the same time, consider the following
batch file:
*** Einstein.BAT ***
@echo off
cls
map m:=sys1:mail >>nul
m:
mail.exe
mailpop.exe
This way, no matter what happens the MAILPOP.EXE file will be executed
after the MAIL.EXE program, in effect invoking the program. It does not
matter if the program is already loaded or not. If it is not, it will be
loaded. If it is, then it will be popped up and made active.
┌──────┐
│ Hey! │
└──────┘
Einstein, Einstein E-Mail, and MailRoom are trademarks of Devont Software, Inc.
IBM PC, XT, AT and PS/2 are trademarks of International Business Machines, Inc.
Novell is a trademark of Novell, Inc.
MHS is a trademark of Novell, Inc.
Saber is a trademark of Saber Software Corp.
WP Office is a trademark of WordPerfect Corporation.
WordPerfect is a trademark of WordPerfect Corporation.
Hercules is a trademark of Hercules, Inc.
Microsoft Windows is a trademark of Microsoft, Inc.
All other trademarks in this document are trademarks of their respetive holders